Crowdsec integration: update health check command from capi to lapi#707
Merged
SunsetDrifter merged 1 commit intonetbirdio:mainfrom Apr 20, 2026
Merged
Conversation
SunsetDrifter
approved these changes
Apr 20, 2026
Contributor
|
@blotus Thank you very much!!! |
Contributor
|
Thanks. This one fell through the cracks. I already corrected it in the code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
Crowdsec maintainer here !
I just saw that you've added an integration with crowdsec in your latest release, thanks !
After a quick look at your documentation, I spotted an issue in the example compose file: you are using
cscli capi statusas the health check for the container, but this command is not intended to be used like this.cscli capi statuswill attempt to login to the central API (hosted by us), and this tells nothing about the state of the local instance, but simply that the instance has valid CAPI credentials.The command that you actually want to use is
cscli lapi status: this will query the local API running in the container.The Pangolin team made the same mistake a few months back, and we had to put in place more drastic rate limiting on CAPI for instances querying too often (see this issue for more context), so a check every 10s will definitely lead to very harsh rate limiting.
This PR simply replaces
capiwithlapiin the health check command, and in the command used to verify if the container is up before adding a new bouncer.